ULTIMATE TRADING TOOLS - UTT UPGRADED 2026 BOT PACK
===================================================
268 bots rebuilt for dbot.ultimatedigits.ai and ultimateblocks.tools (stock Deriv blocks + the sites' own
extra blocks only - no apollo/btnotify/Binary-Bot-2019 dialect left). Every file passed a rendered Blockly load
against the real block definitions with zero block loss. Full per-bot notes: UTT UPGRADE REPORT.md

HOW TO USE
1. Upload the XML on either site (Bot Builder > Load).
2. Open "1. Trade parameters" > "Run once at start" - all settings are the UTT | ... variables at the top:
   UTT | Base Stake            starting stake (lifted from the bot's own stake where it had one)
   UTT | MM System (0-7)       0 Flat, 1 Martingale (default), 2 D'Alembert, 3 Oscar's Grind, 4 1-3-2-6,
                               5 Reverse Martingale, 6 Reverse D'Alembert, 7 = the bot's ORIGINAL staking logic
   UTT | Martingale Multiplier used by systems 1 and 5
   UTT | Max Stake             hard cap on any stake
   UTT | Take Profit / Stop Loss   session limits on total profit - bot notifies and stops
   UTT | Loss Streak Reset     consecutive losses after which the stake goes back to base
3. Optional trade parameters on Volatility bots: "Alternate markets" and "Scan all volatility markets" (off by default).
4. The stake goes through the "licensed stake ... for ultimateblocks.tools | dbot.ultimatedigits.ai" block.
   It only passes on those two platforms; anywhere else the stake is refused and the bot stops. Deleting the
   block removes the stake, so the bot cannot be unlocked by editing it out.

MARKETS / DURATIONS
Verified live against Deriv contracts_for on 2026-09-08. Digit bots run on 1 tick; Higher/Lower, Touch, Reset,
Asians on 5-10 ticks; Only Ups/Downs 2-5 ticks; accumulators on Volatility or Boom/Crash at 1-5 % growth.
Bots that were on a market that does not offer their contract were moved (see report).

NOT INCLUDED
Poverty X Pro DBot (Tradecity).xml - the source file is 28 KB of null bytes (corrupted), nothing to rebuild.
Two "(2)" byte-identical copies were folded into one output each.
